Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix backtraces feature #1613

Merged
merged 5 commits into from
Mar 6, 2023
Merged

Conversation

toml01
Copy link
Contributor

@toml01 toml01 commented Feb 22, 2023

The backtraces feature seems to be broken for a while now, this commit fixes it.

Comment on lines -5 to +6
#![cfg_attr(feature = "backtraces", feature(backtrace))]
#![cfg_attr(feature = "backtraces", feature(error_generic_member_access))]
#![cfg_attr(feature = "backtraces", feature(provide_any))]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you are putting into life those changes from thiserror: https://github.com/dtolnay/thiserror/pull/182/files

@webmaster128
Copy link
Member

Thank you for bringing this up, @toml01. Happy to look into it.

However, could you keep the PR minimal and specific to one thing? It seems like the whole lockfile is updated for no reason, including a bump of schemars and as a result newly generated JSON Schemas. This is cool, but should get its own PR.

You can sue the dev scripts from the main README to only perform minimal lockfile updates:

# Updates ./Cargo.lock
./devtools/check_workspace.sh

# Updates ./contracts/**/Cargo.lock
./devtools/check_contracts_fast.sh

@webmaster128
Copy link
Member

The schemars upgrade is now here: #1617

@toml01
Copy link
Contributor Author

toml01 commented Mar 5, 2023

@webmaster128 yeah I was just trying to make the tests pass.
But np, I will revert the rest of the commits and will pull from main

@toml01 toml01 force-pushed the fix-backtraces-feature branch from 4edc542 to 4eb3279 Compare March 5, 2023 09:49
@toml01
Copy link
Contributor Author

toml01 commented Mar 5, 2023

@webmaster128 I think it looks good now, lmk if I can do anything else :)

Copy link
Member

@webmaster128 webmaster128 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks a lot!

@webmaster128
Copy link
Member

Published as part of 1.2.2 today

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants